31 March 2025

Windcave

Windcave is a third party supplier which is integrated with ebs to process online payments. You must contact Windcave to agree a contract.

When you have negotiated a contract with Windcave, you are ready to start the configuration with ebs. At this point you should have received a URL from Windcave that is specific to your organisation.

Configuration

You must configure ePayments before configuring the payment provider.

The institution settings for Windcave are configured on the following screens (accessed from the Product Modules pane):

Data Sent to Windcave

The data sent to Windcave when making a payment is described in table Data sent to Windcave.

Data sent to Windcave
Value Source Notes
PxPayUserId Payment Account Id As defined in institution settings
PxPayPayKey Payment Account Key As defined in institution settings
TxnId The ePayment transaction ID Generated from EPAYMENT_TRANSACTION_ID_SEQ DB sequence when creating the payment
AmountInput The total amount being paid None
CurrencyInput The CurrencyCode institution setting ('CurrencyCode') None
EmailAddress Email Address from the payment details Uses the Default Payment Email Address institution setting if user does not have one defined
MerchantReference The Payment Merchant Reference institution setting None
TxnType 'Payment' None
TxnData1 The first 250 bytes of the payment details (pid) token None
TxnData2 The second 250 bytes of the payment details (pid) token None
TxnData3 The third 250 bytes of the payment details (pid) token None
UrlFail The URL used to report back the status of the failed payment This is the server path appended with /epayments/PaymentResponse.aspx
UrlSucceed The URL used to report back the status of the successful payment This is the server path appended with /epayments/PaymentResponse.aspx

Refer to PCI Compliance for further information about how ebs interacts with Windcave.